Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium

ABSTRACT

The present disclosure aims to provide a core node capable of appropriately allocating a radio resource of a RAN Slice allocated for a specific service to a radio terminal that uses this specific service. A core node ( 10 ) according to the present disclosure includes: a determination unit ( 14 ) configured to determine a radio resource to be allocated in accordance with a service provided for a radio terminal ( 30 ); and a communication unit ( 12 ) configured to transmit resource identification information indicating the radio resource determined in the determination unit ( 14 ) to a base station ( 20 ) that manages a plurality of radio resources for each RAN Slice associated with a service.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 16/520,448 entitled “CORE NODE, BASE STATION, RADIO TERMINAL,COMMUNICATION METHOD, RADIO RESOURCE ALLOCATION METHOD, BASE STATIONSELECTION METHOD, AND READABLE MEDIUM,” filed Jul. 24, 2019, whichclaims benefit of the priority of U.S. patent application Ser. No.16/083,577 entitled “CORE NODE, BASE STATION, RADIO TERMINAL,COMMUNICATION METHOD, RADIO RESOURCE ALLOCATION METHOD, BASE STATIONSELECTION METHOD, AND READABLE MEDIUM,” filed Sep. 10, 2018, whichclaims the benefit of the priority of national stage application ofInternational Application No. PCT/JP2017/006644 entitled “CORE NODE,BASE STATION, RADIO TERMINAL, COMMUNICATION METHOD, RADIO RESOURCEALLOCATION METHOD, BASE STATION SELECTION METHOD, AND READABLE MEDIUM,”filed on Feb. 22, 2017, which claims the benefit of the priority toJapanese Patent Application No. 2016-058260, filed on Mar. 23, 2016, thedisclosures of each of the above are hereby incorporated by reference intheir entirety.

TECHNICAL FIELD

The present disclosure relates to a core node, a base station, a radioterminal, a communication method, a radio resource allocation method, abase station selection method, and a program, and more specifically, toa core node, a base station, a radio terminal, a communication method, aradio resource allocation method, a base station selection method, and aprogram for performing allocation of radio resources.

BACKGROUND ART

In recent years, discussions on Internet Of Things (IoT) services havebeen conducted. In the IoT services, a large number of terminals thatautonomously execute communications (each of these terminals will bereferred to as an IoT terminal) without requiring any user's operationhave been used. Therefore, in order to provide the IoT services using alarge number of IoT terminals, it has been desired to efficientlyaccommodate a large number of IoT terminals in a network that acommunication provider or the like manages.

Non-Patent Literature 1 discloses, in page 11, a method of managingradio resources to be allocated to terminals. Specifically, thisliterature discloses that a radio resource group including a pluralityof radio resources is divided into a plurality of Radio Access Network(RAN) Slices and each of the RAN Slices is allocated to a specificservice. That is, the radio resources included in a predetermined RANSlice are allocated to the radio terminal used for a specific service.As described above, by allocating the RAN Slice for each service, it ispossible to prevent radio resources from not being allocated to otherservices when the number of radio terminals used for a specific servicehas increased.

CITATION LIST Non-Patent Literature

-   [Non-Patent Literature 1] Vision on 5G Radio Access Technologies,    Huawei Technologies, 3GPP RAN workshop on 5G, Sep. 17-18, 2015,    Phoenix, USA, RWS-150006

SUMMARY OF INVENTION Technical Problem

However, while dividing a radio resource group into a plurality of RANSlices and managing the plurality of RAN Slices are disclosed inNon-Patent Literature 1, this literature does not disclose how toallocate radio resources to the radio terminal. That is, a method ofallocating the radio resources to the radio terminal used for a specificservice has not yet been established. The method of allocating the radioresources is the method of allocating the radio resources of the RANSlice allocated for a specific service to the radio terminal. Therefore,there is a problem that it is impossible to allocate the radio resourcesof the RAN Slice that are managed in a divided manner to an appropriateradio terminal.

The present disclosure aims to provide a core node, a base station, aradio terminal, a communication method, a radio resource allocationmethod, a base station selection method, and a program capable ofappropriately allocating radio resources of a RAN Slice allocated foreach service to the radio terminal that uses this service.

Solution to Problem

A core node according to a first aspect of the present disclosureincludes: a determination unit configured to determine a radio resourceto be allocated in accordance with a service provided for a radioterminal; and a communication unit configured to transmit resourceidentification information indicating the radio resource determined inthe determination unit to a base station that manages a plurality ofradio resources for each RAN Slice associated with a service.

A base station according to a second aspect of the present disclosureincludes: a management unit configured to manage a plurality of radioresources for each RAN Slice associated with a service; a communicationunit configured to receive resource identification information that hasbeen transmitted from a core node and indicates a radio resource to beallocated in accordance with a service provided for a radio terminal;and a resource allocation unit configured to allocate the radio resourceindicated by the resource identification information to the radioterminal.

A radio terminal according to a third aspect of the present disclosureincludes: a receiver configured to receive broadcast information itemstransmitted from a plurality of respective base stations; and adetermination unit configured to determine that the radio terminalshould be connected to a base station among the plurality of basestations that has transmitted broadcast information including RAN Sliceidentification information indicating a RAN Slice that provides aservice that the radio terminal uses.

A communication method according to a fourth aspect of the presentdisclosure includes: determining a radio resource to be allocated inaccordance with a service to be provided for a radio terminal; andtransmitting resource identification information indicating the radioresource that has been determined to a base station that manages aplurality of radio resources for each RAN Slice associated with aservice.

A radio resource allocation method according to a fifth aspect of thepresent disclosure includes: managing a plurality of radio resources foreach RAN Slice associated with a service; receiving resourceidentification information that has been transmitted from a core nodeand indicates a radio resource to be allocated in accordance with aservice provided for a radio terminal; and allocating the radio resourceindicated by the resource identification information to the radioterminal.

A base station selection method according to a sixth aspect of thepresent disclosure includes: receiving broadcast information itemstransmitted from a plurality of respective base stations; anddetermining that a connection should be established with a base stationamong the plurality of base stations that has transmitted broadcastinformation including RAN Slice identification information indicating aRAN Slice that provides a service to be used.

A program according to a seventh aspect of the present disclosure causesa computer to execute the following processing of: determining a radioresource to be allocated in accordance with a service to be provided fora radio terminal; and transmitting resource identification informationindicating the radio resource that has been determined to a base stationthat manages a plurality of radio resources for each RAN Sliceassociated with a service.

Advantageous Effects of Invention

According to the present disclosure, it is possible to provide a corenode, a base station, a radio terminal, a communication method, a radioresource allocation method, a base station selection method, and aprogram capable of appropriately allocating radio resources of a RANSlice allocated for each service to the radio terminal that uses thisservice.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a configuration diagram of a communication system according toa first embodiment;

FIG. 2 is a configuration diagram of a communication system according toa second embodiment;

FIG. 3 is a configuration diagram of a UE according to the secondembodiment;

FIG. 4 is a configuration diagram of radio resource managed by an eNodeBaccording to the second embodiment;

FIG. 5 is a diagram showing information managed by each node apparatusaccording to the second embodiment;

FIG. 6 is a diagram showing a flow of an Attach procedure according tothe second embodiment;

FIG. 7 is a diagram showing a flow of the Attach procedure according tothe second embodiment;

FIG. 8 is a diagram showing a flow of a UE triggered Service Requestprocedure according to the second embodiment;

FIG. 9 is a diagram showing a flow of the UE triggered Service Requestprocedure according to the second embodiment;

FIG. 10 is a diagram showing a flow of an Attach procedure according toa third embodiment;

FIG. 11 is a diagram showing a flow of a UE triggered Service Requestprocedure according to the third embodiment;

FIG. 12 is a configuration diagram of a communication system accordingto a fourth embodiment;

FIG. 13 is a diagram showing a flow of a Combined GPRS/IMSI AttachProcedure according to the fourth embodiment;

FIG. 14 is a diagram showing a flow of a PDP Context ActivationProcedure for Iu mode according to the fourth embodiment;

FIG. 15 is a diagram showing a flow of the PDP Context ActivationProcedure for Iu mode according to the fourth embodiment;

FIG. 16 is a diagram showing a flow of an MS Initiated Service RequestProcedure using GN/Gp according to the fourth embodiment;

FIG. 17 is a diagram showing the MS Initiated Service Request Procedureusing GN/Gp according to the fourth embodiment;

FIG. 18 is a diagram showing a flow of a PDP Context ActivationProcedure for Iu mode according to a fifth embodiment;

FIG. 19 is a diagram showing a flow of an MS Initiated Service RequestProcedure using GN/Gp according to the fifth embodiment;

FIG. 20 is a configuration diagram of a base station according to eachembodiment;

FIG. 21 is a configuration diagram of a radio terminal according to eachembodiment; and

FIG. 22 is a configuration diagram of a core node according to eachembodiment.

DESCRIPTION OF EMBODIMENTS First Embodiment

Hereinafter, with reference to the drawings, embodiments of the presentdisclosure will be explained. With reference to FIG. 1, a configurationexample of a communication system according to a first embodiment of thepresent disclosure will be explained. FIG. 1 includes a core node 10, abase station 20, and a radio terminal 30. The core node 10, the basestation 20, and the radio terminal 30 may each be a computer apparatusoperated by a processor executing a program stored in a memory.

The core node 10 may be a Mobility Management Entity (MME), a ServingGeneral Packet Radio Service Support Node (SGSN) or the like eachdefined to be a node that performs session management and mobilitymanagement in the 3rd Generation Partnership Project (3GPP) The basestation 20 may be an evolved Node B (eNodeB) that is defined in the3GPP. The eNodeB is a base station that supports Long Term Evolution(LTE) as a radio communication system. Further, the base station 20 maybe replaced by a Radio Network Controller (RNC) and a NodeB defined tobe an apparatus for controlling the base station in the 3GPP.

The radio terminal 30 may be a mobile phone terminal, a smartphoneterminal, a tablet terminal or the like. Alternatively, the radioterminal 30 may be an IoT terminal, a Machine Type Communication (MTC)terminal, a Machine to Machine (M2M) terminal or the like.

Next, a configuration example of the core node 10 will be explained. Thecore node 10 includes a communication unit 12 and a determination unit14. The components that compose the core node 10 such as thecommunication unit 12 and the determination unit 14 may be software or amodule whose processing is executed by the processor executing theprogram stored in the memory. Alternatively, the components that formthe core node 10 may be hardware such as a circuit or a chip. Further,the communication unit 12 includes a transmitter and a receiver.

The determination unit 14 determines radio resources to be allocated tothe radio terminal 30 using service information indicating the serviceto be provided for the radio terminal 30. The radio resources may be,for example, resources managed by the base station 20. The radioresources may be resources defined using at least one of a frequency andtime.

The service to be provided for the radio terminal 30 may be, forexample, a voice service for providing a voice call, a data service fortransmitting image data, text data or the like, a simultaneousdistribution service for concurrently distributing data or the like.Alternatively, the service to be provided for the radio terminal 30 maybe an IoT service. The IoT service may be, for example, a service thatuses a smart meter, an automatic driving service or the like. Theservices stated as the service to be provided for the radio terminal 30are not limited to the aforementioned services and various kinds ofservices may be provided for the radio terminal 30. The serviceinformation is information for identifying the service to be providedfor the radio terminal 30.

The communication unit 12 transmits resource identification informationindicating the radio resources determined in the determination unit 14to the base station 20 that divides the radio resource group includingthe plurality of radio resources into a plurality of RAN Slices andmanages the plurality of RAN Slices. Each of the RAN Slices includessome radio resources included in the radio resource group. Each of theRAN Slices includes at least one radio resource. One radio resource maybe, for example, a resource that is specified using a specific frequencyband and a specified period. It can also be said that the RAN Sliceincludes an area in which a plurality of radio resources are combinedwith each other. Further, it can be said that the RAN Slice includes atleast some of the radio resource groups managed by the base station 20.The RAN Slice is associated with the service provided for the radioterminal. That is, the RAN Slice includes at least one radio resource tobe allocated to the radio terminal that uses the specific service.

The resource identification information, which is information foridentifying the radio resources managed by the base station 20, isinformation for identifying at least one radio resource. Further, thecommunication unit 12 transits resource identification informationindicating the radio resources included in the RAN Slice associated withthe service to be provided for the radio terminal 30 to the base station20.

Next, a configuration example of the base station 20 will be explained.The base station 20 includes a communication unit 22, a management unit24, and a resource allocation unit 26. The components such as thecommunication unit 22, the management unit 24, and the resourceallocation unit 26 that compose the base station 20 may be software or amodule whose processing is executed by the processor executing theprogram stored in the memory. Alternatively, the components that composethe base station 20 may be hardware such as a circuit or a chip.Further, the communication unit 22 includes a transmitter and areceiver.

The management unit 24 divides a radio resource group including theplurality of radio resources into a plurality of RAN Slices and managesthe plurality of RAN Slices. The communication unit 22 receives theresource identification information that has been transmitted from thecore node 10 and indicates the radio resources to be allocated to theradio terminal 30. The resource identification information indicates theradio resources included in the RAN Slice associated with the service tobe provided for the radio terminal 30.

The resource allocation unit 26 allocates the radio resources indicatedin the resource identification information to the radio terminal 30.

As described above, by using the communication system shown in FIG. 1,the core node 10 is able to transmit the resource identificationinformation indicating the radio resource to be allocated to the radioterminal 30 to the base station 20 that divides the radio resource groupinto a plurality of RAN Slices and manages the plurality of RAN Slices.Therefore, the base station 20 is able to allocate the radio resourcesspecified by the core node 10 to the radio terminal 30. The core node 10is able to determine the radio resources to be allocated to the radioterminal 30 based on the service used by the radio terminal 30.Therefore, the base station 20 is able to appropriately allocate theradio resources included in the RAN Slice associated with the serviceused by the radio terminal 30 to the radio terminal 30.

Second Embodiment

Referring next to FIG. 2, a configuration example of a communicationsystem according to a second embodiment of the present disclosure willbe explained. The communication system shown in FIG. 2 is acommunication system that supports LTE as a radio communication system,and is a communication system defined to be an Evolved Packet System(EPS) in the 3GPP. FIG. 2 is based on the drawing in TS 23.401 V 13.5.0FIG. 4.2.1-1.

The communication system shown in FIG. 2 includes a User Equipment (UE)40, an Evolved-Universal Mobile Telecommunications System TerrestrialRadio Access Network (E-UTRAN) 41, an MME 42, a Home Subscriber Server(HSS) 43, an SGSN 44, a Serving Gateway (SGW) 45, a Packet Data NetworkGateway (PGW) 46, a Policy and Charging Rules Function (PCRF) entity 47(hereinafter it will be referred to as a PCRF 47), a UTRAN 48, a GlobalSystem for Mobile communications (GSM) (trademark) Enhanced Data Ratesfor Global Evolution (EDGE) Radio Access Network (GERAN) 49, and anOperator's IP Services 50.

The UE 40 is used as a general term for the radio terminal in the 3GPP.The UE may be replaced by, for example, a Mobile Station (MS). TheE-UTRAN 41 is a Radio Access Network (RAN) that uses LTE as a radioaccess system. The UTRAN 48 is a RAN that uses a 3G wireless system as aradio access system. The GERAN 49 is a RAN that uses a 2G wirelesssystem as a radio access system.

Each of the MME 42 and the SGSN 44 is a node that executes mobilitymanagement, session management and the like regarding the UE 40. The HSS43 is a node that manages subscriber information regarding the UE 40.The subscriber information includes information regarding the servicethat the UE 40 uses. The SGW 45 and the PGW 46 are nodes that relay datatransmitted between the UE 40 and the Operator's IP Services 50. TheOperator's IP Services 50 may be, for example, a server apparatus orserver apparatuses managed by a provider or the like that provides aservice for the UE 40. The PCRF 47 is a node that manages policy andcharging rules and the like.

An LTE-Uu reference point is defined between the UE 40 and the E-UTRAN41. An S1-MME reference point is defined between the E-UTRAN 41 and theMME 42. An S6 reference point is defined between the MME 42 and the HSS43. An S3 reference point is defined between the MME 42 and the SGSN 44.An S1-U reference point is defined between the E-UTRAN 41 and the SGW45. An S11 reference point is defined between the MME 42 and the SGW 45.An S4 reference point is defined between the SGSN 44 and the SGW 45. AnS12 reference point is defined between the SGW 45 and the UTRAN 48. AnS5/S8 reference point is defined between the SGW 45 and the PGW 46. A Gxreference point is defined between the PGW 46 and the PCRF 47. An SGireference point is defined between the PGW 46 and the Operator's IPServices 50. An Rx reference point is defined between the PCRF 47 andthe Operator's IP Services 50. An S1-10 reference point is definedbetween the MME 42 and another MME.

Referring next to FIG. 3, a configuration example of the UE 40 will beexplained. The UE 40 includes a communication unit 71, a RAN Sliceavailability determination unit 72, and a connection destination RANSlice selection unit 73. The components that form the UE 40 may besoftware or a module whose processing is executed by the processorexecuting the program stored in the memory. Alternatively, thecomponents that form the UE 40 may be hardware such as a circuit, a chipor the like.

The communication unit 71 performs radio communication with the eNodeBincluded in the E-UTRAN 41 using LTE. Further, the communication unit 71receives broadcast information transmitted from the eNodeB. Thecommunication unit 71 may receive broadcast information from a pluralityof eNodeBs. The broadcast information is transmitted using, for example,a Broadcast Control Channel (BCCH). The broadcast information includesat least one RAN Slice ID. The RAN Slice ID is information foridentifying the RAN Slice managed by the eNodeB. Further, the RAN Sliceis a radio resource that is used to provide a specific service. That is,the UE 40 is able to recognize the service that the eNodeB can provideby receiving the broadcast information. The communication unit 71outputs the RAN Slice ID included in the broadcast information to theRAN Slice availability determination unit 72.

The RAN Slice availability determination unit 72 determines whetherthere is a RAN Slice associated with a service that the UE 40 uses inthe RAN Slice ID output from the communication unit 71. It is assumedthat the RAN Slice availability determination unit 72 stores at leastone RAN Slice ID indicating the RAN Slice associated with the servicethat the UE 40 uses in advance. The RAN Slice availability determinationunit 72 determines whether the RAN Slice ID that is stored in advance isincluded in the RAN Slice ID output from the communication unit 71. TheRAN Slice availability determination unit 72 outputs the RAN Slice IDthat coincides with the RAN Slice ID that is stored in advance fromamong the RAN Slice IDs output from the communication unit 71 to theconnection destination RAN Slice selection unit 73.

When the connection destination RAN Slice selection unit 73 has receiveda plurality of RAN Slice IDs from the RAN Slice availabilitydetermination unit 72, the connection destination RAN Slice selectionunit 73 selects, based on the predetermined policy, the RAN Slice to beused. The connection destination RAN Slice selection unit 73 may select,for example, the RAN Slice ID that has been transmitted from the eNodeBwhose radio field intensity is the strongest. Alternatively, theconnection destination RAN Slice selection unit 73 may set prioritiesfor the respective RAN Slice IDs and select the RAN Slice ID whosepriority is the highest. The connection destination RAN Slice selectionunit 73 outputs the RAN Slice ID that has been selected to thecommunication unit 71. Alternatively, the connection destination RANSlice selection unit 73 may select the RAN Slice ID regarding thespecific service to be preferentially used. The specific service is, forexample, an IoT service, an automatic driving service or the like.

The communication unit 71 executes connection processing with the eNodeBincluding the RAN Slice ID output from the connection destination RANSlice selection unit 73.

Referring next to FIG. 4, a configuration example of the radio resourcesmanaged by the eNodeB included in the E-UTRAN 41 according to the secondembodiment of the present disclosure will be explained. FIG. 4 showsthat the eNodeB manages a radio resource group including a plurality ofradio resources. FIG. 4 further shows that the eNodeB divides the radioresource group into a RAN Slice #A and a RAN Slice #B and manages theseRAN Slices. FIG. 4 further shows that the RAN Slice #A is formed of aplurality of radio resource groups to be allocated to a specific group.The specific group may be, for example, a group that uses the serviceassociated with the RAN Slice #A. The specific group may include aplurality of UEs that use the service associated with the RAN Slice #A.The RAN Slice #A may be, for example, a RAN Slice for automatic driving.Further, the specific group may be an automatic driving apparatusprovided by each company. Radio resources included in the radio resourcegroup allocated to the group to which the UE belongs are allocated tothe UE. The radio resources to be allocated to the UE are identified by,for example, a Resource ID.

Referring next to FIG. 5, information included in the UE 40, the eNodeB,the MME 42, the HSS 43, and the information management apparatus will beexplained. The information management apparatus, which is an apparatusdifferent from the HSS 43, manages subscriber information. While the HSS43 and the information management apparatus are shown to be apparatusesdifferent from each other in FIG. 5, the HSS 43 and the informationmanagement apparatus may be the same apparatus. In other words, the HSS43 may include the function of the information management apparatus.

The UE 40 includes an Internal Mobile Subscriber identity (IMSI) and aRAN Slice ID. The IMSI is information for identifying the UE. The RANSlice ID is information indicating the RAN Slice associated with aservice that the UE 40 uses.

The eNodeB manages the RAN Slice ID and the Resource ID in associationwith each other. The RAN Slice ID is information for identifying the RANSlice managed by the eNodeB. The Resource ID is information foridentifying the radio resources to be allocated to the UE 40. TheResource ID is information uniquely identified in the eNodeB. One RANSlice ID and a plurality of Resource IDs are associated with each other.Further, when the eNodeB manages a plurality of RAN Slices, it includesa plurality of RAN Slice IDs.

The HSS 43 manages the IMSI and the UE Usage type in association witheach other. The UE Usage type is information for identifying the servicethat the UE identified by the IMSI uses or the group to which the UEbelongs. The HSS 43 manages the IMSI and the UE Usage type regarding theplurality of UEs.

The information management apparatus manages the Service ID and the UEUsage type in association with each other. The Service ID is informationfor identifying the service that the UE uses and the group to which theUE belongs. It is assumed that the Service ID is information uniquelyidentified in the communication system. The information managementapparatus manages the Service ID and the UE Usage type regarding aplurality of UEs. When the HSS 43 and the information managementapparatus are the same apparatus, the HSS 43 manages the IMSI, the UEUsage type, and the Service ID in association with one another. Theservice that the UE uses is specified using the Service ID. Further, theService ID is specified using the UE Usage type. The Service ID may bespecified using subscriber information other than the UE Usage type.

The MME 42 manages the Service ID and the Resource ID in associationwith each other. That is, the MME 42 is able to specify the Resource IDto be allocated to the UE in the eNodeB using the Service ID.

While the eNodeB manages the radio resources using the Resource IDuniquely identified in the eNodeB in FIG. 5, the eNodeB may manage theradio resources using the Service ID uniquely identified in thecommunication system. In this case, the MME 42 needs not manage theService ID and the Resource ID and is able to send an instructionregarding the radio resources to be allocated to the UE to the eNodeBusing the Service ID.

Referring next to FIG. 6, a flow of the Attach procedure according tothe second embodiment of the present disclosure will be explained. FIG.6 shows a flow of processing when the Attach procedure is normallycompleted in the communication system shown in FIG. 2. The Attachprocedure shown in FIG. 6 is based on TS23.401 V13.5.0 (2015-12) FIG.5.3.2.1-1: Attach procedure. In the Attach procedure shown in FIG. 6,regarding processing similar to that in TS23.401 V13.5.0 (2015-12) FIG.5.3.2.1-1: Attach procedure, detailed descriptions thereof will beomitted.

Further, the UE shown in FIG. 6 corresponds to the UE 40 shown in FIG. 2and the eNodeB shown in FIG. 6 corresponds to the eNodeB included in theE-UTRAN 41 shown in FIG. 2. The new MME shown in FIG. 6 corresponds tothe MME 42 shown in FIG. 2. The Old MME/SGSN shown in FIG. 6 is theMME/SGSN that has been allocated to the UE 40 in the previous Attach. Inthe Attach procedure shown in FIG. 6, an operation of a case in which anMME (new MME) other than the MME/SGSN (Old MME/SGSN) allocated in theprevious Attach is allocated due to, for example, a movement of the UE40, will be explained. The Serving GW shown in FIG. 6 corresponds to theSGW 45 shown in FIG. 2. The PDN GW shown in FIG. 6 corresponds to thePGW 46 shown in FIG. 2. The PCRF shown in FIG. 6 corresponds to the PCRF47 shown in FIG. 2. The HSS shown in FIG. 6 corresponds to the HSS 43shown in FIG. 2. Further, the Equipment Identity Register (EIR) shown inFIG. 6 is a node that manages identification information (e.g., a MobileEquipment (ME) identity) of the UE, although it is not shown in FIG. 2.

Since FIG. 6, 1 to FIG. 6, 7 are similar to the processing shown inTS23.401 V13.5.0 (2015-12) FIG. 5.3.2.1-1: Attach procedure, detaileddescriptions thereof will be omitted. In the processing of FIG. 6, 1 toFIG. 6, 7, authentication processing regarding the UE is mainlyexecuted.

When the processing of FIG. 6, 1 to FIG. 6, 7 is completed, the new MMEtransmits an Update Location Request message to the HSS (FIG. 6, 8). TheUpdate Location Request message includes the IMSI of the UE. Since FIG.6, 9 and FIG. 6, 10 are similar to the processing shown in TS23.401V13.5.0 (2015-12) FIG. 5.3.2.1-1: Attach procedure, detaileddescriptions thereof will be omitted. In the processing of FIG. 6, 9 andFIG. 6, 10, processing for deleting information regarding the UE managedin the Old MME/SGSN is mainly executed.

When the HSS acquires the IMSI of the UE in FIG. 6, 8, the HSS specifiesthe UE Usage type associated with the acquired IMSI. Further, the HSSacquires the Service ID associated with the specified UE Usage type fromthe information management apparatus. When the HSS and the informationmanagement apparatus are the same apparatus, the HSS further specifiesthe Service ID associated with the specified UE Usage type using thespecified UE Usage type.

The HSS transmits an Update Location Ack message to the new MME (FIG. 6,11). The Update Location Ack message includes a Service ID.

Since FIG. 6, 12 to FIG. 6, 16 are similar to the processing shown inTS23.401 V13.5.0 (2015-12) FIG. 5.3.2.1-1: Attach procedure, detaileddescriptions thereof will be omitted. In FIG. 6, 12 to FIG. 6, 16,processing for establishing the session and the bearer that the UE usesbetween the Serving GW and the PDN GW is mainly executed.

When the new MME acquires the Service ID that identifies the servicethat the UE uses and the group to which the UE belongs in FIG. 6, 11,the new MME specifies the Resource ID that specifies the radio resourceto be allocated to the UE in the eNodeB. The Resource ID is associatedwith the Service ID. When the new MME specifies the Resource ID, the newMME transmits an Initial Context Setup Request message to the eNodeB(FIG. 6, 17). The Initial Context Setup Request message includes aResource ID.

Next, the eNodeB determines whether it is possible to allocate, to theUE, the radio resources indicated by the Resource ID transmitted fromthe new MME. When, for example, the radio resources indicated by theResource ID are not allocated to another UE, the eNodeB may be able todetermine that it is possible to allocate the radio resources indicatedby the Resource ID transmitted from the new MME. When the eNodeBdetermines that it is possible to allocate the radio resources indicatedby the Resource ID transmitted from the new MME to the UE, the eNodeBtransmits an RRC Connection Reconfiguration message to the UE (FIG. 6,18). The RRC Connection Reconfiguration message includes information forspecifying the radio resources indicated by the Resource ID transmittedfrom the new MME. The information for specifying the radio resources maybe, for example, identification information of a frequency and a timeslot indicating the radio resources. Therefore, the UE is notified thatthe UE is allowed to allocate the radio resource included in the RANSlice regarding the service thereto.

Since FIG. 6, 19 to FIG. 6, 26 are similar to the processing shown inTS23.401 V13.5.0 (2015-12) FIG. 5.3.2.1-1: Attach procedure, detaileddescriptions thereof will be omitted. In FIG. 6, 19 to FIG. 6, 26,processing for notifying the Serving GW of information regarding theradio bearer established between the UE and the eNodeB is mainlyexecuted.

Referring next to FIG. 7, a flow of the Attach procedure according tothe second embodiment of the present disclosure will be explained. FIG.7 shows a flow of processing when the Attach procedure is not normallycompleted in the communication system shown in FIG. 2. Since FIG. 7, 1to FIG. 7, 17 are similar to FIG. 6, the descriptions thereof will beomitted.

When the eNodeB receives the Initial Context Setup Request messageincluding the Resource ID in FIG. 7, 17, the eNodeB determines whetherit is possible to allocate the radio resources indicated by the ResourceID to the UE.

In this example, when the eNodeB has determined that it is impossible toallocate, to the UE, the radio resources indicated by the Resource IDtransmitted from the new MME, the eNodeB transmits the Initial ContextSetup Response message to the new MME without transmitting the RRCConnection Reconfiguration message to the UE (FIG. 7, 18). This InitialContext Setup Response message includes information indicating that itis impossible to allocate the radio resources to the UE.

Next, the new MME transmits the Attach Reject message to the UE via theeNodeB (FIG. 7, 19). The new MME notifies the UE that the Attachprocedure has not normally completed by transmitting the Attach Rejectmessage to the UE. Therefore, the UE is notified that the radio resourceincluded in the RAN Slice regarding the service that the UE uses can beallocated thereto.

Referring next to FIG. 8, a flow of the UE triggered Service Requestprocedure according to the second embodiment of the present disclosurewill be explained. FIG. 8 shows a flow of processing when the UEtriggered Service Request procedure is normally completed in thecommunication system shown in FIG. 2. The UE triggered Service Requestprocedure is, for example, processing executed when the UE starts datatransmission, starts an outgoing call or the like. As a premise that theUE triggered Service Request procedure is executed, the Attach procedurehas been normally completed and the MME manages the subscriberinformation regarding the UE.

The UE triggered Service Request procedure shown in FIG. 8 is based onTS23.401 V13.5.0 (2015-12) FIG. 5.3.4.1-1: UE triggered Service Requestprocedure. In the UE triggered Service Request procedure shown in FIG.8, regarding the processing similar to TS23.401 V13.5.0 (2015-12) FIG.5.3.4.1-1: UE triggered Service Request procedure, detailed descriptionsthereof will be omitted.

First, the UE transmits the NAS Service Request message to the MME viathe eNodeB (FIG. 8, 1 and FIG. 8, 2). The MME specifies the Service IDassociated with the UE using the subscriber information regarding theUE. Next, authentication processing regarding the UE is executed betweenthe UE and the MME and further between the MME and the HSS (FIG. 8, 3).

Next, the MME transmits the S1-AP: Initial Context Setup Request messageincluding the Resource ID associated with the specified Service ID tothe eNodeB (FIG. 8, 4).

Next, the eNodeB determines whether it is possible to allocate, to theUE, the radio resources indicated by the Resource ID transmitted fromthe MME. When the eNodeB determines that it is possible to allocate theradio resources indicated by the Resource ID transmitted from the newMME to the UE, the eNodeB performs Radio Bearer Establishment processingin order to allocate the radio resources indicated by the Resource ID tothe UE (FIG. 8, 5). Since the processing of FIG. 8, 6 and the followingprocessing are similar to TS23.401 V13.5.0 (2015-12) FIG. 5.3.4.1-1: UEtriggered Service Request procedure, detailed descriptions thereof willbe omitted. In the processing of FIG. 8, 6 and the following processing,processing for notifying the Serving GW and the PDN GW of theinformation regarding the radio bearer established between the UE andthe eNodeB is mainly executed.

Referring next to FIG. 9, a flow of the UE triggered Service Requestprocedure according to the second embodiment of the present disclosurewill be explained. FIG. 9 shows a flow of processing in which the UEtriggered Service Request procedure is not normally completed in thecommunication system shown in FIG. 2. Since FIG. 9, 1 to FIG. 9, 4 aresimilar to FIG. 8, the descriptions thereof will be omitted.

When the eNodeB receives the S1-AP: Initial Context Setup Requestmessage including the Resource ID in FIG. 9, 4, the eNodeB determineswhether it is possible to allocate the radio resources indicated by theResource ID to the UE.

In this example, when the eNodeB has determined that it is impossible toallocate, to the UE, the radio resources indicated by the Resource IDtransmitted from the MME, the eNodeB transmits the S1-AP: InitialContext Setup Response message to the MME without executing the RadioBearer Establishment processing (FIG. 9, 5). The S1-AP: Initial ContextSetup Response message includes information indicating that it isimpossible to allocate the radio resources to the UE.

Next, the MME transmits the NAS: Service Reject message to the UE viathe eNodeB (FIG. 9, 6). The MME notifies the UE that the UE triggeredService Request procedure has not normally completed by transmitting theNAS: Service Reject message to the UE.

As described above, by using the communication system according to thesecond embodiment of the present disclosure, the MME is able to specifythe radio resources to be allocated to the UE based on the service thatthe UE uses and the group to which the UE belongs. Specifically, the MMEis able to specify the radio resources included in the RAN Sliceassociated with the service that the UE uses. Accordingly, the eNodeB isable to allocate the radio resources included in the RAN Slice to the UEthat uses the service associated with the RAN Slice. As a result, theeNodeB is able to prevent the radio resources included in the RAN Sliceassociated with a service different from the service that the UE usesfrom being allocated to this UE.

Further, the MME is able to specify the radio resources to be allocatedto the UE using the Service ID identifying the group to which the UEbelongs. Accordingly, when the RAN Slice is formed of a radio resourcegroup to be allocated to a plurality of specific groups, it is possibleto prevent the radio resources to be allocated to a group other than thegroup to which the UE belongs from being allocated to this UE.

Further, the eNodeB is able to determine whether it is possible toallocate the radio resources included in the Resource ID specified fromthe MME to the UE. Accordingly, when the UE receives, from the eNodeB, anotification indicating that it is impossible to allocate radioresources to the UE, the UE is able to re-select an eNodeB that providesthe service that the UE uses, the eNodeB being another eNodeB includingavailable radio resources.

Third Embodiment

Next, a flow of processing when the Attach procedure is normallycompleted according to the third embodiment of the present disclosurewill be explained. In this example, processing different from the flowof processing in FIG. 6 will be mainly explained. In the secondembodiment, the eNodeB determines whether it is possible to allocate theradio resources indicated by the Resource ID to the UE. On the otherhand, in the third embodiment, the MME determines whether it is possibleto allocate the radio resources indicated by the Resource ID to the UE.

It is assumed that the eNodeB periodically transmits, to the MME,information indicating the state in which the radio resources areallocated. That is, it is assumed that the MME holds informationindicating the state in which the radio resources of the eNodeB areallocated. In this case, when the new MME receives the Update LocationAck message including the Service ID in FIG. 6, 11, this MME determineswhether it is possible to allocate the Resource ID associated with theService ID to the UE. When the new MME determines that it is possible toallocate the radio resources to the UE, it executes the processing ofFIG. 6, 12 and the following processing. However, unlike the processingin the second embodiment, when the eNodeB receives the Initial ContextSetup Request message in FIG. 6, 17, the eNodeB does not executeprocessing for determining whether it is possible to allocate radioresources to the UE.

Referring next to FIG. 10, a flow of processing when the Attachprocedure is not normally completed according to the third embodiment ofthe present disclosure will be explained. Since FIG. 10, 1 to FIG. 10,11 are similar to FIG. 6, 1 to FIG. 6, 11, the descriptions thereof willbe omitted.

When the new MME receives the Update Location Ack message including theService ID in FIG. 10, 11, the new MME determines whether it is possibleto allocate the Resource ID associated with the Service ID to the UE.When the new MME has determined that it is impossible to allocate theradio resources to the UE, it transmits the Attach Reject message to theUE via the eNodeB without executing the processing of FIG. 6, 12 and thefollowing processing (FIG. 10, 12). The new MME notifies the UE that theAttach procedure has not normally completed by transmitting the AttachReject message to the UE.

Next, a flow of processing when the UE triggered Service Requestprocedure is normally completed according to the third embodiment of thepresent disclosure will be explained. In this example, processingdifferent from the flow of processing in FIG. 8 will be mainlyexplained. In the second embodiment, the eNodeB determines whether it ispossible to allocate the radio resources indicated by the Resource ID tothe UE. On the other hand, in the third embodiment, the MME determineswhether it is possible to allocate the radio resources indicated by theResource ID to the UE.

It is assumed that the eNodeB periodically transmits, to the MME,information indicating the state in which the radio resources areallocated. That is, it is assumed that the MME holds informationindicating the state in which the radio resources of the eNodeB areallocated.

In this case, when the MME receives the NAS: Service Request message inFIG. 8, 2, the MME specifies the Service ID using the subscriberinformation regarding the UE, and further specifies the Resource IDassociated with the Service ID. The MME determines whether it ispossible to allocate the radio resources indicated by the Resource ID tothe UE. When the MME determines that it is possible to allocate theradio resources to the UE, the MME executes the processing of FIG. 8, 4and the following processing. However, unlike the processing in thesecond embodiment, when the eNodeB has received the S1-AP: InitialContext Setup Request message in FIG. 8, 4, the eNodeB does not executeprocessing for determining whether it is possible to allocate radioresources to the UE.

Referring next to FIG. 11, a flow of processing when the UE triggeredService Request procedure is not normally completed according to thethird embodiment of the present disclosure will be explained. Since FIG.11, 1 to FIG. 11, 3 are similar to FIG. 8, 1 to FIG. 8, 3, thedescriptions thereof will be omitted.

When the MME receives the NAS: Service Request message in FIG. 11, 2,the MME specifies the Service ID using the subscriber informationregarding the UE, and further specifies the Resource ID associated withthe Service ID. The MME determines whether it is possible to allocatethe radio resources indicated by the Resource ID to the UE. When the MMEhas determined that it is impossible to allocate the radio resources tothe UE, the MME transmits the NAS: Service Reject message to the UE viathe eNodeB without executing the processing of FIG. 8, 4 and thefollowing processing (FIG. 11, 4 and FIG. 11, 5). The MME notifies theUE that the UE triggered Service Request procedure has not normallycompleted by transmitting the NAS: Service Reject message to the UE.

As described above, by using the communication system according to thethird embodiment of the present disclosure, the MME is able to determinewhether it is possible to allocate the radio resources indicated by thespecified Resource ID to the UE. Accordingly, when the MME determinesthat it is impossible to allocate the radio resources, it is possible tostop the Attach procedure and the UE triggered Service Request procedurewithout executing a plurality of processing including processing forconfiguring the radio bearer between the eNodeB and the UE. Therefore,it is possible to reduce the number of messages in the Attach procedureand the UE triggered Service Request procedure in the case in which theMME has determined that it is impossible to allocate the radio resourcesrelative to the number of messages in the second embodiment.

Fourth Embodiment

Referring next to FIG. 12, a configuration example of a communicationsystem according to a fourth embodiment of the present disclosure willbe explained. The communication system shown in FIG. 12, which is acommunication system that supports a 3G radio communication system as aradio communication system, is a communication system defined to be theGPRS in the 3GPP.

The communication system shown in FIG. 12 includes an MS 60, a UTRAN 61,an SGSN 62, a Gateway GPRS Support Node (GGSN) 63, a Home LocationRegister (HLR) 64, a Packet Data Network (PDN) 65, a Mobile SwitchingCenter (MSC)/Visited Location Register (VLR) 66, and an EIR 67.

The MS 60 is used as a general term for the radio terminal in the 3GPP.The MS may be replaced by, for example, UE. The configuration of the MS60 is similar to that of the UE 40 shown in FIG. 3. The UTRAN 61 is aRAN that uses a 3G wireless system as a radio access system. The UTRAN61 includes an RNC.

The SGSN 62 is a node that executes mobility management, sessionmanagement and the like regarding the MS 60. The HLR 64 is a node thatmanages the subscriber information regarding the MS 60. The subscriberinformation includes information regarding the service that the MS 60uses. The GGSN 63 is a node that relays data transmitted between the MS60 and the PDN 65. The PDN 65 may be, for example, a network including aserver apparatus or server apparatuses managed by a provider or the likethat provides a service to the MS 60.

The MSC/VLR 66, which includes a Circuit Switched function, is a nodethat manages the subscriber information regarding the MS. The EIR 67 isa node that manages identification information on the MS (e.g., IMEI:International Mobile Equipment Identity).

A Uu reference point is defined between the MS 60 and the UTRAN 61. AnIu reference point is defined between the UTRAN 61 and the SGSN 62. A Gnreference point is defined between the SGSN 62 and the GGSN 63. A Grreference point is defined between the SGSN 62 and the HLR 64. A Gcreference point is defined between the GGSN 63 and the HLR 64. A Gireference point is defined between the GGSN 63 and the PDN 65. An Iureference point is defined between the UTRAN 61 and the MSC/VLR 66. A Gsreference point is defined between the SGSN 62 and the MSC/VLR 66. A Dreference point is defined between the HLR 64 and the MSC/VLR 66. A Gpreference point is defined between the SGSN 62 and the EIR 67.

The configuration of the radio resources managed in the RNC included inthe UTRAN 61 is similar to that shown in FIG. 4. That is, the radioresource group managed by the eNodeB in FIG. 4 is replaced by the radioresource group managed by the RNC.

The information included in the MS 60, the RNC, the SGSN 62, the HLR 64,and the information management apparatus is similar to that shown inFIG. 5. That is, the UE 40 shown in FIG. 5 is replaced by the MS 60, theeNodeB shown in FIG. 5 is replaced by the RNC, the MME 42 shown in FIG.5 is replaced by the SGSN 62, and the HSS 43 shown in FIG. 5 is replacedby the HLR 64.

Referring next to FIG. 13, a Combined GPRS/IMSI Attach Procedureaccording to the fourth embodiment of the present disclosure will beexplained. FIG. 13 shows a flow of processing when the CombinedGPRS/IMSI Attach Procedure is normally completed in the communicationsystem shown in FIG. 12. The Combined GPRS/IMSI Attach Procedure shownin FIG. 13 is based on TS23.060 V13.5.0 (2015-12) FIG. 22: CombinedGPRS/IMSI Attach Procedure. In A Combined GPRS/IMSI Attach Procedure inFIG. 13, regarding the processing similar to that in TS23.060 V13.5.0(2015-12) FIG. 22: Combined GPRS/IMSI Attach Procedure, detaileddescriptions thereof will be omitted.

Further, the MS in FIG. 13 corresponds to the MS 60 shown in FIG. 12.The RAN in FIG. 13 corresponds to the UTRAN 61 shown in FIG. 12. The newSGSN shown in FIG. 13 corresponds to the SGSN 62 shown in FIG. 12. Theold SGSN shown in FIG. 13 is the SGSN that has been allocated to the MS60 in the previous Combined GPRS/IMSI Attach Procedure. In the CombinedGPRS/IMSI Attach Procedure shown in FIG. 13, an operation of a case inwhich an SGSN (new SGSN) different from the SGSN (Old SGSN) allocated inthe previous Combined GPRS/IMSI Attach Procedure has been allocated dueto, for example, a movement of the MS 60, will be explained.

The GGSN shown in FIG. 13 corresponds to the GGSN 63 shown in FIG. 12.The HLR shown in FIG. 13 corresponds to the HLR 64 shown in FIG. 12. Thenew MSC/VLR shown in FIG. 13 corresponds to the MSC/VLR 66 shown in FIG.12. The old MSC/VLR shown in FIG. 13 is an MSC/VLR allocated to the MS60 in the previous Combined GPRS/IMSI Attach Procedure. The EIR shown inFIG. 13 corresponds to the EIR 67 shown in FIG. 12.

Since FIG. 13, 1 to FIG. 13, 6 are similar to the processing shown inTS23.060 V13.5.0 (2015-12) FIG. 22: Combined GPRS/IMSI Attach Procedure,detailed descriptions thereof will be omitted. In the processing of FIG.13, 1 to FIG. 13, 6, authentication processing regarding the MS ismainly executed.

When the processing of FIG. 13, 1 to FIG. 13, 6 is completed, the newSGSN transmits the Update Location Request message to the HLR (FIG. 13,7 a). The Update Location Request message includes the IMSI of the MS.Since FIG. 13, 7 b to FIG. 13, 7 e are similar to the processing shownin TS23.060 V13.5.0 (2015-12) FIG. 22: Combined GPRS/IMSI AttachProcedure, detailed descriptions thereof will be omitted. In theprocessing of FIG. 13, 7 b to FIG. 13, 7 e, processing for deletinginformation regarding the MS managed in OldSGSN is mainly executed.

When the HLR acquires the IMSI of the MS in FIG. 13, 7 a, the HLRspecifies the UE Usage type associated with the acquired IMSI. Further,the HLR acquires the Service ID associated with the specified UE Usagetype from the information management apparatus. When the HLR and theinformation management apparatus are the same apparatus, the HLR furtherspecifies the Service ID associated with the specified UE Usage typeusing the specified UE Usage type.

The HLR transmits an Insert Subscriber Data message to the new SGSN(FIG. 13, 7 f). The Insert Subscriber Data message includes a ServiceID.

Since FIG. 13, 7 g to FIG. 13, 8 h are similar to the processing shownin TS23.060 V13.5.0 (2015-12) FIG. 22: Combined GPRS/IMSI AttachProcedure, detailed descriptions thereof will be omitted. In FIG. 13, 7g to FIG. 13, 8 h, processing for registering the SGSN and the MSC/VLRallocated in the Attach Procedure this time in the HLR is mainlyexecuted.

While it has been described that the Service ID is included in theInsert Subscriber Data message in FIG. 13, 7 f, the Service ID may beincluded in the Update Location Ack message in FIG. 13, 7 h.

Since FIG. 13, 9 to FIG. 13, 12 are similar to the processing shown inTS23.060 V13.5.0 (2015-12) FIG. 22: Combined GPRS/IMSI Attach Procedure,detailed descriptions thereof will be omitted. In FIG. 13, 9 to FIG. 13,12, processing in accordance with the completion of the Attach Procedureis mainly executed.

Referring next to FIG. 14, a PDP Context Activation Procedure for Iumode according to the fourth embodiment of the present disclosure willbe explained. The PDP Context Activation Procedure for Iu mode shown inFIG. 14 is based on TS23.060 V13.5.0 (2015-12) FIG. 64: PDP ContextActivation Procedure for Iu mode. In the PDP Context ActivationProcedure for Iu mode in FIG. 14, regarding the processing similar tothat in TS23.060 V13.5.0 (2015-12) FIG. 64: PDP Context ActivationProcedure for Iu mode, detailed descriptions thereof will be omitted.

The PDP Context Activation Procedure for Iu mode is, for example,processing that is executed when the MS starts transmitting data orstarts an outgoing call. As a premise that the PDP Context ActivationProcedure for Iu mode is executed, it is assumed that the Attachprocedure has been normally completed and the SGSN manages thesubscriber information regarding the MS.

First, the MS transmits the Activate PDP Context Request message to theSGSN via RAN (FIG. 14, 1). The SGSN specifies the Service ID associatedwith the MS using the subscriber information of the MS. Since FIG. 14, 4is the processing similar to TS23.060 V13.5.0 (2015-12) FIG. 64: PDPContext Activation Procedure for Iu mode, detailed descriptions thereofwill be omitted. In FIG. 14, 4, processing for establishing a session ora bearer used by the MS between the SGSN and the GGSN is mainlyexecuted.

The SGSN notifies the RAN of the Resource ID associated with thespecified Service ID in the Radio Access Bearer processing (FIG. 14, 5).Further, the RAN determines whether it is possible to allocate, to theMS, the radio resources indicated by the Resource ID regarding which anotification has been sent from the SGSN. When the RAN has determinedthat it is possible to allocate, to the MS, the radio resourcesindicated by the Resource ID transmitted from the SGSN, the RANallocates the radio resources indicated by the Resource ID to the MS inthe Radio Access Bearer Setup processing in FIG. 14, 5. Since theprocessing of FIG. 14, 6 and the following processing are similar toTS23.060 V13.5.0 (2015-12) FIG. 64: PDP Context Activation Procedure forIu mode, detailed descriptions thereof will be omitted. Regarding theprocessing shown in FIG. 8, 6 and the following processing, processingfor notifying the GGSN of information regarding the radio bearerestablished between the MS and the RAN is mainly executed.

Referring next to FIG. 15, a flow of the PDP Context ActivationProcedure for Iu mode according to the fourth embodiment of the presentdisclosure will be explained. FIG. 15 shows a flow of processing whenthe PDP Context Activation Procedure for Iu mode is not normallycompleted in the communication system shown in FIG. 12. Since FIG. 15, 1and FIG. 15, 4 are similar to FIG. 14, the descriptions thereof will beomitted.

The SGSN transmits a RAB Assignment Request message including theResource ID to the RAN (FIG. 15, 7). When the RAN receives the RABAssignment Request message including the Resource ID in FIG. 15, 7, theRAN determines whether it is possible to allocate the radio resourcesindicated by the Resource ID to the MS.

When the RAN determines that it is impossible to allocate the radioresources indicated by the Resource ID transmitted from the SGSN to theMS, the RAN transmits the RAB Assignment Response message to the SGSNwithout establishing the radio bearer between the RAN and the MS (FIG.15, 7).

Next, the SGSN transmits or receives a Delete PDP ContextRequest/Response message to or from the GGSN in order to delete the PDPContext with the GGSN set in FIG. 15, 4 (FIG. 15, 8).

Next, the SGSN transmits the Activate PDP Context Reject message to theMS via the RAN (FIG. 15, 9). The SGSN notifies the MS that the PDPContext Activation Procedure for Iu mode has not normally completed bytransmitting the Activate PDP Context Reject message to the MS.

Referring next to FIG. 16, an MS Initiated Service Request Procedureusing GN/Gp according to the fourth embodiment of the present disclosurewill be explained. The MS Initiated Service Request Procedure usingGN/Gp shown in FIG. 16 is based on TS23.060 V13.5.0 (2015-12) FIG. 50:MS Initiated Service Request Procedure using GN/Gp. In the MS initiatedService Request Procedure using GN/Gp shown in FIG. 16, regardingprocessing similar to that in TS23.060 V13.5.0 (2015-12) FIG. 50: MSinitiated Service Request Procedure using GN/Gp, detailed descriptionsthereof will be omitted.

FIG. 16 shows a flow of processing of a case in which the MS InitiatedService Request Procedure using GN/Gp is normally completed in thecommunication system shown in FIG. 12. The MS Initiated Service RequestProcedure using GN/Gp is, for example, processing that is executed whenthe MS starts transmitting data or starts an outgoing call. As a premisethat the MS Initiated Service Request Procedure using GN/Gp is executed,it is assumed that the Attach procedure has been normally completed andthe SGSN manages the subscriber information regarding the MS.

In FIG. 16, the RAN in FIGS. 13 to 15 is described to be the RNCincluded in the UTRAN 61. Since FIG. 16, 1 is similar to the processingshown in TS23.060 V13.5.0 (2015-12) FIG. 50: MS Initiated ServiceRequest Procedure using GN/Gp, detailed descriptions thereof will beomitted.

Next, the MS transmits the Service Request message to the SGSN via theRNC (FIG. 16, 2). The SGSN specifies the Service ID associated with theMS using the subscriber information regarding the MS. Next,authentication processing regarding the MS is executed between the MSand the RNC, between the RNC and the SGSN, and between the SGSN and theHLR (FIG. 16, 3).

Next, the SGSN transmits a Radio Access Bearer Assignment Requestmessage including the Resource ID associated with the specified ServiceID to the RNC (FIG. 16, 4).

Next, the RNC determines whether it is possible to allocate, to the MS,the radio resources indicated by the Resource ID transmitted from theSGSN. When the RNC has determined that it is possible to allocate, tothe MS, the radio resources indicated by the Resource ID transmittedfrom the SGSN, the RNC transmits a Radio Bearer Setup message in orderto allocate the radio resources indicated by the Resource ID to the MS(FIG. 16, 5). Since processing of FIG. 16, 6 and the followingprocessing are similar to TS23.060 V13.5.0 (2015-12) FIG. 50: MSInitiated Service Request Procedure using GN/Gp, detailed descriptionsthereof will be omitted.

Referring next to FIG. 17, the MS Initiated Service Request Procedureusing GN/Gp according to the fourth embodiment of the present disclosurewill be explained. FIG. 17 shows a flow of processing when the MSinitiated Service Request Procedure using GN/Gp is not normallycompleted in the communication system shown in FIG. 12.

Since FIG. 17, 1 to FIG. 17, 4 are similar to FIG. 16, 1 to FIG. 16, 4,the descriptions thereof will be omitted. The RNC determines whether itis possible to allocate, to the MS, the radio resources indicated by theResource ID transmitted from the SGSN in FIG. 17, 4. When the RNCdetermines that it is impossible to allocate, to the MS, the radioresources indicated by the Resource ID transmitted from the SGSN, theRNC transmits a Radio Access Bearer Assignment Response message to theSGSN without transmitting the Radio Bearer Setup message to the MS (FIG.17, 5). Next, the SGSN transmits the Service Reject message to the MSvia the RNC (FIG. 17, 6). The SGSN notifies the MS that the MS InitiatedService Request Procedure using GN/Gp has not normally completed bytransmitting the Service Reject message to the MS.

As described above, by using the communication system according to thefourth embodiment of the present disclosure, similar to the case inwhich the EPS is used, the RAN or the RNC is able to prevent radioresources included in the RAN Slice associated with a service other thanthe service that is used by the MS from being allocated to this MS.

Further, the SGSN is able to specify the radio resources to be allocatedto the MS using the Service ID that identifies the group to which the MSbelongs. Accordingly, when the RAN Slice is formed of a radio resourcegroup allocated to a plurality of specific groups, it is possible toprevent the radio resources allocated to a group different from thegroup to which the MS belongs from being allocated to this MS.

Alternatively, the RAN or the RNC is able to determine whether it ispossible to allocate the radio resources included in the Resource IDspecified by the SGSN to the MS. Accordingly, when the MS receives anotification indicating that it is impossible to allocate radioresources from the RAN, the MS is able to re-select a RAN that providesthe service the MS uses, the RAN being another RAN including availableradio resources.

Fifth Embodiment

Next, a flow of processing when the PDP Context Activation Procedure forIu mode is normally completed according to the fifth embodiment of thepresent disclosure will be explained. In this example, processingdifferent from the flow of the processing in FIG. 14 will be mainlyexplained. In the fourth embodiment, the RAN determines whether it ispossible to allocate, to the MS, the radio resources indicated by theResource ID. On the other hand, in the fifth embodiment, the SGSNdetermines whether it is possible to allocate the radio resourcesindicated by the Resource ID to the MS.

It is assumed that the RAN periodically transmits, to the SGSN,information indicating the state in which the radio resources areallocated. That is, it is assumed that the SGSN holds informationindicating the state in which radio resources of the RAN are allocated.

In this case, when the SGSN receives the Activate PDP Context Requestmessage in FIG. 14, 1, the SGSN specifies the Service ID using thesubscriber information regarding the MS, and further specifies theResource ID associated with the Service ID. The SGSN determines whetherit is possible to allocate the radio resources indicated by the ResourceID to the MS. When the SGSN determines that it is possible to allocatethe radio resources to the MS, the SGSN executes processing of FIG. 14,4 and the following processing. However, the RAN does not execute theprocessing for determining whether it is possible to allocate the radioresources to the MS in FIG. 14, 5.

Referring next to FIG. 18, a flow of processing when the PDP ContextActivation Procedure for Iu mode is not normally completed according tothe fifth embodiment of the present disclosure will be explained. SinceFIG. 18, 1 is similar to FIG. 14, 1, the descriptions thereof will beomitted.

When the SGSN receives the Activate PDP Context Request message in FIG.18, 1, the SGSN specifies the Service ID using the subscriberinformation regarding the MS, and further specifies the Resource IDassociated with the Service ID. The SGSN determines whether it ispossible to allocate the radio resources indicated by the Resource ID tothe MS. When the SGSN determines that it is impossible to allocate theradio resources to the MS, the SGSN transmits the Activate PDP ContextReject message to the MS via RAN without executing the processing ofFIG. 14, 4 and the following processing (FIG. 18, 2). The SGSN notifiesthe UE that the PDP Context Activation Procedure for lea mode has notnormally completed by transmitting the Activate PDP Context Rejectmessage to the MS.

Next, a flow of processing when the MS Initiated Service RequestProcedure using GN/Gp is normally completed according to the fifthembodiment of the present disclosure will be explained. In this example,processing different from the flow of the processing in FIG. 16 will bemainly explained. In the fourth embodiment, the RAN determines whetherit is possible to allocate the radio resources indicated by the ResourceID to the MS. On the other hand, in the fifth embodiment, the SGSNdetermines whether it is possible to allocate the radio resourcesindicated by the Resource ID to the MS.

It is assumed that the RAN periodically transmits, to the SGSN,information indicating the state in which the radio resources areallocated. That is, it is assumed that the SGSN holds informationindicating the state in which the radio resources of the RAN areallocated.

In this case, when the SGSN receives the Service Request message in FIG.16, 2, the SGSN specifies the Service ID using the subscriberinformation regarding the MS, and further specifies the Resource IDassociated with the Service ID. The SGSN determines whether it ispossible to allocate the radio resources indicated by the Resource ID tothe MS. The SGSN executes the processing of FIG. 16, 3 and the followingprocessing when the SGSN determines that it is possible to allocate theradio resources to the MS. However, the RAN does not execute theprocessing for determining whether it is possible to allocate the radioresources to the MS in FIG. 16, 4.

Referring next to FIG. 19, a flow of processing when the MS InitiatedService Request Procedure using GN/Gp is not normally completedaccording to the fifth embodiment of the present disclosure will beexplained. Since FIG. 19, 1 to FIG. 19, 3 are similar to FIG. 16, 1 toFIG. 16, 3, the descriptions thereof will be omitted.

When the SGSN receives the Service Request message in FIG. 19, 2, theSGSN specifies the Service ID using the subscriber information regardingthe MS, and further specifies the Resource ID associated with theService ID. The SGSN determines whether it is possible to allocate theradio resources indicated by the Resource ID to the MS. When the SGSNdetermines that it is impossible to allocate the radio resources to theMS, the SGSN transmits the Service Reject message to the MS via the RNCwithout executing the processing of FIG. 16, 4 and the followingprocessing (FIG. 19, 4). The SGSN notifies the UE that the MS InitiatedService Request Procedure using GN/Gp has not normally completed bytransmitting the Service Reject message to the MS.

As described above, by using the communication system according to thefifth embodiment of the present disclosure, the SGSN is able todetermine whether it is possible to allocate the radio resourcesindicated by the specified Resource ID to the UE. Accordingly, when theSGSN determines that it is impossible to allocate the radio resources,it is possible to stop the Attach procedure, the PDP Context ActivationProcedure for Iu mode, and the MS Initiated Service Request Procedureusing GN/Gp without executing a plurality of processing includingprocessing for configuring a radio bearer between the RAN (RNC) and theMS. Therefore, it is possible to reduce the number of messages of theAttach procedure, the PDP Context Activation Procedure for Iu mode, andthe MS initiated Service Request Procedure using GN/Gp in the case inwhich the SGSN has determined that it is impossible to allocate theradio resources.

Next, in the following description, configuration examples of the corenode 10, the base station 20, and the radio terminal 30 described in theaforementioned embodiments will be explained. FIG. 20 is a block diagramshowing a configuration example of the base station 20. Referring toFIG. 20, the base station 20 includes an RF transceiver 1001, a networkinterface 1003, a processor 1004, and a memory 1005. The RIF transceiver1001 performs analog RF signal processing to communicate with the UEs.The RF transceiver 1001 may include a plurality of transceivers. The RFtransceiver 1001 is coupled to an antenna 1002 and the processor 1004.The RF transceiver 1001 receives modulated symbol data (or OFDM symboldata) from the processor 1004, generates a transmission RF signal, andsupplies the transmission RF signal to the antenna 1002. Further, the RFtransceiver 1001 generates a baseband reception signal based on areception RF signal received by the antenna 1002 and supplies thissignal to the processor 1004.

The network interface 1003 is used to communicate with the network node(e.g., core node 10). The network interface 1003 may include, forexample, a network interface card (NIC) conforming to the IEEE 802.3series.

The processor 1004 performs data plane processing including digitalbaseband signal processing and control plane processing for radiocommunication. In the case of LTE and LTE-Advanced, for example, thedigital baseband signal processing by the processor 1004 may includesignal processing of the MAC layer and the PHY layer.

The processor 1004 may include a plurality of processors. The processor1004 may include, for example, a modem processor (e.g., DSP) thatperforms the digital baseband signal processing and a protocol stackprocessor (e.g., a CPU or an MPU) that performs the control planeprocessing.

The memory 1005 is composed of a combination of a volatile memory and anon-volatile memory. The memory 1005 may include a plurality of memorydevices that are physically independent from each other. The volatilememory is, for example, a Static Random Access Memory (SRAM), a DynamicRAM (DRAM), or a combination thereof. The non-volatile memory is, forexample, a Mask Read Only Memory (SROM), an Electrically ErasableProgrammable ROM (EEPROM), a flash memory, a hard disc drive, or anycombination thereof. The memory 1005 may include a storage that islocated apart from the processor 1004. In this case, the processor 1004may access the memory 1005 via the network interface 1003 or an I/Ointerface (not shown).

The memory 1005 may store a software module (computer program) includinginstructions and data for performing processing by the base station 20described in the aforementioned embodiments. In some implementations,the processor 1004 may load the software module from the memory 1005 andexecute the loaded software module, thereby performing the processing ofthe remote node 10 described in the aforementioned embodiments.

FIG. 21 is a block diagram showing a configuration example of the radioterminal 30. A Radio Frequency (RF) transceiver 1101 performs analog RFsignal processing to communicate with the base station 20. The analog RFsignal processing performed by the RF transceiver 1101 includesfrequency up-conversion, frequency down-conversion, and amplification.The RF transceiver 1101 is coupled to an antenna 1102 and a basebandprocessor 1103. That is, the RF transceiver 1101 receives modulatedsymbol data (or OFDM symbol data) from the baseband processor 1103,generates a transmission RF signal, and supplies the transmission RFsignal to the antenna 1102. Further, the RF transceiver 1101 generates abaseband reception signal based on a reception RF signal received by theantenna 1102, and supplies the baseband reception signal to the basebandprocessor 1103.

The baseband processor 1103 performs digital baseband signal processing(i.e., data plane processing) and control plane processing for radiocommunication. The digital baseband signal processing includes (a) datacompression/decompression, (b) data segmentation/concatenation, (c)composition/decomposition of a transmission format (i.e., transmissionframe), (d) channel coding/decoding, (e) modulation (i.e., symbolmapping)/demodulation, and (f) generation of OFDM symbol data (i.e.,baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). On theother hand, the control plane processing includes communicationmanagement of layer 1 (e.g., transmission power control), layer 2 (e.g.,radio resource management and hybrid automatic repeat request (HARQ)processing) and layer 3 (e.g., signaling regarding attach, mobility, andcall management).

In the case of LTE and LTE-Advanced, for example, the digital basebandsignal processing by the baseband processor 1103 may include signalprocessing of a Packet Data Convergence Protocol (PDCP) layer, a RadioLink Control (RLC) layer, a MAC layer, and a PHY layer. Further, thecontrol plane processing by the baseband processor 1103 may includeprocessing of a Non-Access Stratum (NAS) protocol, an RRC protocol, andMAC CE.

The baseband processor 1103 may include a modem processor (e.g., aDigital Signal Processor (DSP)) that performs the digital basebandsignal processing and a protocol stack processor (e.g., a CentralProcessing Unit (CPU) or a Micro Processing Unit (MPU)) that performsthe control plane processing. In this case, the protocol stackprocessor, which performs control plane processing, may be integratedwith an application processor 1104 described in the following.

The application processor 1104 is also referred to as a CPU, an MPU, amicroprocessor, or a processor core. The application processor 1104 mayinclude a plurality of processors (processor cores). The applicationprocessor 1104 executes a system software program (Operating System(OS)) and various application programs (e.g., a voice call application,a WEB browser, a mailer, a camera operation application, and a musicplayer application) loaded from a memory 1106 or from another memory(not shown), thereby providing various functions of the radio terminal30.

In some implementations, as represented by a dashed line (1105) in FIG.21, the baseband processor 1103 and the application processor 1104 maybe integrated on a single chip. In other words, the baseband processor1103 and the application processor 1104 may be implemented in a singleSystem on Chip (SoC) device 1105. An SoC device may be referred to as asystem Large Scale Integration (LSI) or a chipset.

The memory 1106 is a volatile memory, a non-volatile memory, or acombination thereof. The memory 1106 may include a plurality of memorydevices that are physically independent from each other. The volatilememory is, for example, a Static Random Access Memory (SRAM), a DynamicRAM (DRAM), or a combination thereof. The non-volatile memory is, forexample, a Mask Read Only Memory (MROM), an Electrically ErasableProgrammable ROM (EEPROM), a flash memory, a hard disc drive, or anycombination thereof. The memory 1106 may include, for example, anexternal memory device that can be accessed from the baseband processor1103, the application processor 1104, and the SoC 1105. The memory 1106may include an internal memory device that is integrated in the basebandprocessor 1103, the application processor 1104, or the SoC 1105.Further, the memory 1106 may include a memory in a Universal IntegratedCircuit Card (UICC).

The memory 1106 may store a software module (computer program) includinginstructions and data for performing processing by the radio terminal 30described in the aforementioned embodiments. In some implementations,the baseband processor 1103 or the application processor 1104 may loadthe software module from the memory 1106 and execute the loaded softwaremodule, thereby performing the processing of the radio terminal 30described in the aforementioned embodiments.

FIG. 22 is a block diagram showing the configuration example of the corenode 10. Referring to FIG. 22, a center node 20 includes a networkinterface 1201, a processor 1202, and a memory 1203. The networkinterface 1201 is used to communicate with the network node (e.g., thebase station 20). The network interface 1201 may include, for example, anetwork interface card (NIC) conforming to the IEEE 802.3 series.

The processor 1202 loads software (computer program) from the memory1203 and executes the loaded software, thereby performing the processingof the core node 10 described with reference to the sequence diagramsand flowcharts in the aforementioned embodiments. The processor 1202 maybe, for example, a microprocessor, an MPU, or a CPU. The processor 1202may include a plurality of processors.

The processor 1202 performs data plane processing including digitalbaseband signal processing and control plane processing for radiocommunication. In the case of LTE and LTE-Advanced, for example, thedigital baseband signal processing by the processor 1004 may includesignal processing of the PDCP layer, the RLC layer, and the MAC layer.Further, the signal processing by the processor 1202 may include signalprocessing of the GTP-U·UDP/IP layer in the X2-U interface and the S1-Uinterface. Further, the control plane processing by the processor 1004may include processing of the X2AP protocol, the S1-MME protocol, andthe RRC protocol.

The processor 1202 may include a plurality of processors. The processor1004 may include, for example, a modem processor (e.g., a DSP) thatperforms the digital baseband signal processing, a processor (e.g., DSP)that performs the signal processing of the GTP-U·UDP/IP layer on theX2-U interface and the S1-U interface, and a protocol stack processor(e.g., a CPU or an MPU that performs the control plane processing.

The memory 1203 is composed of a combination of a volatile memory and anon-volatile memory. The memory 1203 may include a storage that islocated apart from the processor 1202. In this case, the processor 1202may access the memory 1203 via an I/O interface (not shown).

In the example shown in FIG. 22, the memory 1203 is used to storesoftware modules. The processor 1202 loads these software modules fromthe memory 1203 and executes these loaded software modules, therebyperforming the processing of the core node 10 described in theaforementioned embodiments.

As described above with reference to FIGS. 20 to 22, each of theprocessors included in the base station 20, the radio terminal 30, andthe core node 10 according to the aforementioned embodiments executesone or more programs including instructions to cause a computer toperform an algorithm described with reference to the drawings.

In the aforementioned examples, the program(s) can be stored andprovided to a computer using any type of non-transitory computerreadable media. Non-transitory computer readable media include any typeof tangible storage media. Examples of non-transitory computer readablemedia include magnetic storage media (such as flexible disks, magnetictapes, hard disk drives, etc.), optical magnetic storage media (e.g.,magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R,CD-R/W, and semiconductor memories (such as mask ROM, Programmable ROM(PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM),etc.). The program(s) may be provided to a computer using any type oftransitory computer readable media. Examples of transitory computerreadable media include electric signals, optical signals, andelectromagnetic waves. Transitory computer readable media can providethe program to a computer via a wired communication line (e.g., electricwires, and optical fibers) or a wireless communication line.

The present disclosure is not limited to the aforementioned embodimentsand may be changed as appropriate without departing from the spirit ofthe present disclosure. Further, the present disclosure may be executedby combining the embodiments as appropriate.

While the present disclosure has been described with reference to theembodiments, the present disclosure is not limited to the aforementionedembodiments. Various changes that can be understood by those skilled inthe art can be made to the configurations and the details of the presentdisclosure within the scope of the present disclosure.

This application is based upon and claims the benefit of priority fromJapanese Patent Application No. 2016-058260, filed on Mar. 23, 2016, thedisclosure of which is incorporated herein in its entirety by reference.

For example, some or all of the embodiments disclosed above can bedescribed as, but not limited to, the following supplementary notes.

(Supplementary Note 1)

A core node comprising:

a determination unit configured to determine a radio resource to beallocated in accordance with a service provided for a radio terminal;and

a communication unit configured to transmit resource identificationinformation indicating the radio resource determined in thedetermination unit to a base station that manages a plurality of radioresources for each RAN Slice associated with a service.

(Supplementary Note 2)

The core node according to Supplementary Note 1, wherein thedetermination unit manages service identification information thatindicates a service that the radio terminal uses and is uniquelyidentified in a mobile core network and the resource identificationinformation in association with each other and acquires the serviceidentification information from a management apparatus that managesterminal identification information of the radio terminal and theservice identification information in association with each other.

(Supplementary Note 3)

The core node according to Supplementary Note 2, wherein the serviceidentification information uniquely identified in the mobile corenetwork is used as the resource identification information.

(Supplementary Note 4)

The core node according to any one of Supplementary Notes 1 to 3,wherein the determination unit determines whether there is a radioresource to be allocated to the radio terminal in a RAN Slice thatprovides a service that is used by the radio terminal based on a usagesituation of a radio resource in the base station.

(Supplementary Note 5)

The core node according to Supplementary Note 4, wherein thecommunication unit transmits a reject message indicating that it isimpossible to allocate a radio resource to the radio terminal via thebase station when it is determined in the determination unit that thereis no radio resource to be allocated to the radio terminal.

(Supplementary Note 6)

A base station comprising:

a management unit configured to manage a plurality of radio resourcesfor each RAN Slice associated with a service:

a communication unit configured to receive resource identificationinformation that has been transmitted from a core node and indicates aradio resource to be allocated in accordance with a service provided fora radio terminal; and

a resource allocation unit configured to allocate the radio resourceindicated by the resource identification information to the radioterminal.

(Supplementary Note 7)

The base station according to Supplementary Note 6, wherein the resourceallocation unit determines whether to allocate the radio resourceindicated by the resource identification information to the radioterminal in accordance with a usage situation of a radio resource.

(Supplementary Note 8)

The base station according to Supplementary Note 7, further comprising acommunication unit configured to transmit a reject message indicatingthat it is impossible to allocate a radio resource to the radio terminalwhen it is determined that there is no radio resource to be allocated tothe radio terminal in the resource allocation unit.

(Supplementary Note 9)

A radio terminal comprising:

a receiver configured to receive broadcast information items transmittedfrom a plurality of respective base stations; and

a determination unit configured to determine that the radio terminalshould be connected to a base station among the plurality of basestations that has transmitted broadcast information including RAN Sliceidentification information indicating a RAN Slice that provides aservice that the radio terminal uses.

(Supplementary Note 10)

The radio terminal according to Supplementary Note 9, wherein thedetermination unit determines, when there are a plurality of basestations that have transmitted broadcast information including RAN Sliceidentification information indicating a RAN Slice that provides aservice to be used, a base station to which the radio terminal isconnected based on radio field intensities of radio waves output fromthe respective base stations.

(Supplementary Note 11)

The radio terminal according to Supplementary Note 9 or 10, wherein thedetermination unit determines, when the determination unit has receiveda reject message indicating that it is impossible to allocate a radioresource from the base station, that the radio terminal should beconnected to a base station other than the base station that has beendetermined, from among a plurality of base stations that havetransmitted broadcast information including RAN Slice identificationinformation indicating a RAN Slice that provides a service to be used.

(Supplementary Note 12)

A communication method comprising:

determining a radio resource to be allocated in accordance with aservice to be provided for a radio terminal; and

transmitting resource identification information indicating the radioresource that has been determined to a base station that manages aplurality of radio resources for each RAN Slice associated with aservice.

(Supplementary Note 13)

A radio resource allocation method comprising:

managing a plurality of radio resources for each RAN Slice associatedwith a service;

receiving resource identification information that has been transmittedfrom a core node and indicates a radio resource to be allocated inaccordance with a service provided for a radio terminal; and

allocating the radio resource indicated by the resource identificationinformation to the radio terminal.

(Supplementary Note 14)

A base station selection method comprising:

receiving broadcast information items transmitted from a plurality ofrespective base stations; and

determining that a connection should be established with a base stationamong the plurality of base stations that has transmitted broadcastinformation including RAN Slice identification information indicating aRAN Slice that provides a service to be used.

(Supplementary Note 15)

A program for causing a computer to execute the following processing of:

determining a radio resource to be allocated in accordance with aservice to be provided for a radio terminal; and

transmitting resource identification information indicating the radioresource that has been determined to a base station that manages aplurality of radio resources for each RAN Slice associated with aservice.

REFERENCE SIGNS LIST

-   10 CORE NODE-   12 COMMUNICATION UNIT-   14 DETERMINATION UNIT-   20 BASE STATION-   22 COMMUNICATION UNIT-   24 MANAGEMENT UNIT-   26 RESOURCE ALLOCATION UNIT-   30 RADIO TERMINAL-   40 UE-   41 E-UTRAN-   42 MME-   43 HSS-   44 SGSN-   45 SGW-   46 PGW-   47 PCRF-   48 UTRAN-   49 GERAN-   50 OPERATOR'S IP SERVICES-   60 MS-   61 UTRAN-   62 SGSN-   63 GGSN-   64 HLR-   65 PDN-   66 MSC/VLR-   67 EIR-   71 COMMUNICATION UNIT-   72 RAN SLICE AVAILABILITY DETERMINATION UNIT-   73 CONNECTION DESTINATION RAN SLICE SELECTION UNIT-   81 CONTROLLER-   82 COMMUNICATION UNIT

The invention claimed is:
 1. A mobility management node in a mobilecommunication system including a data management node, a UE (UserEquipment), and a base station, the mobility management node comprising:at least one processor; and at least one memory coupled to the at leastone processor, the at least one memory storing instructions that whenexecuted by the at least one processor cause the at least one processorto: receive a request message from the UE via the base station, querythe data management node to retrieve UE subscription informationincluding a first ID related to slice information, determine a second IDrelated to the slice information based on the first ID, and send thesecond ID to the UE via the base station.
 2. The mobility managementnode of claim 1, wherein the first ID identifies a service that the UEuses.
 3. The mobility management node of claim 1, wherein the second IDis a resource ID to be allocated to the UE.
 4. A method of a mobilitymanagement node in a mobile communication system including a datamanagement node, a UE (User Equipment), and a base station, the methodcomprising: receiving a request message from the UE via the basestation; querying the data management node to retrieve UE subscriptioninformation including a first ID related to slice information;determining a second ID related to the slice information based on thefirst ID; and sending the second ID to the UE via the base station. 5.The method of claim 4, wherein the first ID identifies a service thatthe UE uses.
 6. The method of claim 4, wherein the second ID is aresource ID to be allocated to the UE.
 7. A UE (User Equipment) in amobile communication system including a data management node, a mobilitymanagement node, and a base station, the UE comprising: at least oneprocessor; and at least one memory coupled to the at least oneprocessor, the at least one memory storing instructions that whenexecuted by the at least one processor cause the at least one processorto: send a request message to the mobility management node via the basestation, the mobility management node querying the data management nodeto retrieve UE subscription information including a first ID related toslice information, and the mobility management node determining a secondID related to the slice information based on the first ID, and receivethe second ID from the mobility management node via the base station. 8.The UE of claim 7, wherein the first ID identifies a service that the UEuses.
 9. The UE of claim 7, wherein the second ID is a resource ID to beallocated to the UE.
 10. A method of a UE (User Equipment) in a mobilecommunication system including a data management node, a mobilitymanagement node, and a base station, the method comprising: sending arequest message to the mobility management node via the base station,the mobility management node querying the data management node toretrieve UE subscription information including a first ID related toslice information, and the mobility management node determining a secondID related to the slice information based on the first ID; and receivingthe second ID from the mobility management node via the base station.11. The method of claim 10, wherein the first ID identifies a servicethat the UE uses.
 12. The method of claim 10, wherein the second ID is aresource ID to be allocated to the UE.